Systems and methods for taking, processing, retrieving, and displaying images from unmanned aerial vehicles

ABSTRACT

A method comprising receiving aerial images captured by one or more unmanned aerial vehicle; receiving metadata associated with the aerial images captured by the one or more unmanned aerial vehicle; geo-referencing the aerial images based on a geographic location of a surface to determine geographic coordinates of pixels of the aerial images; receiving a geographic location from a user; retrieving one or more of the aerial images associated with the geographic location based on the determined geographic coordinates; and displaying to the user one or more overview image depicting the geographic location and overlaid with one or more icons indicative of and associated with the retrieved aerial images associated with the geographic location.

INCORPORATION BY REFERENCE

The present patent application claims priority to the provisional patent application identified by U.S. Ser. No. 62/276,539, filed on Jan. 8, 2016, entitled “Unmanned Aerial Systems and Methods of Using and Controlling Flight of Same,” and to the provisional patent application identified by U.S. Ser. No. 62/413,483, filed on Oct. 27, 2016, entitled “Systems and Methods for Processing Images from Unmanned Aerial Vehicles,” the entire contents of all of which are hereby incorporated herein by reference.

BACKGROUND

Unmanned aerial systems (UAS) typically include unmanned aerial vehicles (UAV) that do not carry a human operator, but instead operate partially or completely autonomously and/or are remotely piloted.

Unmanned aerial vehicles may be used to capture images from one or more onboard image capture device and/or capture sensor data from one or more onboard sensor. In some unmanned aerial systems, the images or sensor data may have embedded metadata. In other unmanned aerial systems, metadata from the time the images or sensor data were taken may be available separately from the unmanned aerial system or from an outside source. However, the format and content type of the images, sensor data, and metadata vary widely depending on the type of unmanned aerial vehicle and/or unmanned aerial system. The form of transmission of the images, sensor data, and metadata also varies widely from system to system.

Therefore, methods and systems are needed to address processing images and accompanying data sourced from diverse unmanned aerial vehicles. Additionally, there is a need for systems and methods to retrieve aerial image and/or sensor data based on the metadata.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 is a block diagram of an exemplary embodiment of an unmanned aerial system in accordance with the present disclosure.

FIG. 2 is a perspective view of an exemplary embodiment of an unmanned aerial system in accordance with the present disclosure.

FIG. 3 is an illustration of another exemplary embodiment of an unmanned aerial system in accordance with the present disclosure.

FIG. 4 is an illustration of yet another exemplary embodiment of an unmanned aerial system in accordance with the present disclosure.

FIG. 5 is a block diagram of an exemplary embodiment of an unmanned aerial vehicle in accordance with the present disclosure.

FIG. 6 is a block diagram of an exemplary embodiment of integrated components of an unmanned aerial vehicle in accordance with the present disclosure.

FIG. 7 is a block diagram of another exemplary embodiment of integrated components of an unmanned aerial vehicle in accordance with the present disclosure.

FIG. 8 is a block diagram of yet another exemplary embodiment of integrated components of an unmanned aerial vehicle in accordance with the present disclosure.

FIG. 9 is an illustration of an exemplary embodiment of multiple unmanned aerial vehicles in accordance with the present disclosure.

FIG. 10 is an illustration of an exemplary embodiment of yet another unmanned aerial vehicle in accordance with the present disclosure.

FIG. 11 is an illustration of the unmanned aerial vehicle of FIG. 10 in which air bladders are deployed.

FIG. 12 is a block diagram of an exemplary embodiment of a bladder system in accordance with the present disclosure.

FIG. 13 is an illustration of exemplary embodiments of unmanned aerial vehicles having closed loop sensors in accordance with the present disclosure.

FIG. 14 is a block diagram of an exemplary embodiment of a controller of an unmanned aerial vehicle in accordance with the present disclosure.

FIG. 15 is a block diagram of an exemplary embodiment of a power system of an unmanned aerial vehicle in accordance with the present disclosure.

FIG. 16 is an illustration of exemplary embodiments of unmanned aerial vehicles having propeller guards in accordance with the present disclosure.

FIG. 17 is a block diagram of an exemplary embodiment of an avionics system of an unmanned aerial vehicle in accordance with the present disclosure.

FIG. 18 is an illustration of exemplary embodiments of unmanned aerial vehicles in accordance with the present disclosure.

FIG. 19 is a block diagram of an exemplary embodiment of a remote station of an exemplary unmanned aerial system in accordance with the present disclosure.

FIG. 20 is a top plan view of an exemplary geographic location.

FIG. 21 is an illustration of an exemplary embodiment of boundary marking of the exemplary geographic location of FIG. 20.

FIG. 22 is an illustration of another exemplary embodiment of boundary marking of the exemplary geographic location of FIG. 20.

FIG. 23 is an illustration of an exemplary embodiment of an unmanned aerial vehicle in use in the exemplary geographic location of FIG. 20.

FIG. 24 is a front view of the unmanned aerial vehicle in use of FIG. 23.

FIG. 25 is a block diagram of an exemplary embodiment of an image location system in accordance with the present disclosure.

FIG. 26 is an exemplary embodiment of an overview image in accordance with the present disclosure.

FIG. 27 is an exemplary embodiment of an overview image having thumbnail images in accordance with the present disclosure.

FIG. 28 is an exemplary embodiment of an overview image having icons in accordance with the present disclosure.

FIG. 29 is an exemplary embodiment of an image in accordance with the present disclosure.

FIG. 30 is an exemplary embodiment of a user search area on an image in accordance with the present disclosure.

FIG. 31 is an exemplary embodiment of a returned image based on the search area of FIG. 30 in accordance with the present disclosure.

FIG. 32 is an exemplary embodiment of another returned image based on the search area of FIG. 30 in accordance with the present disclosure.

FIG. 33 is an exemplary embodiment of another user search area on an image in accordance with the present disclosure.

FIG. 34 is an exemplary embodiment of another user search area on a three dimensional model in accordance with the present disclosure.

FIG. 35 is an exemplary embodiment of another user search area on a three dimensional model in accordance with the present disclosure.

FIG. 36 is an exemplary embodiment of a user search point on a three dimensional model in accordance with the present disclosure.

FIG. 37 is an exemplary embodiment of a user selected wall on a three dimensional model in accordance with the present disclosure.

FIG. 38 is an exemplary embodiment of a user search area on a two dimensional model in accordance with the present disclosure.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

As used herein, the terms “comprises,” “comprising,” “includes,” “including,” “has,” “having” or any other variation thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, article, or apparatus that comprises a list of elements is not necessarily limited to only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Further, unless expressly stated to the contrary, “or” refers to an inclusive “or” and not to an exclusive “or”. For example, a condition A or B is satisfied by anyone of the following: A is true (or present) and B is false (or not present), A is false (or not present) and B is true (or present), and both A and B are true (or present).

In addition, use of the “a” or “an” are employed to describe elements and components of the embodiments herein. This is done merely for convenience and to give a general sense of the inventive concept. This description should be read to include one or more and the singular also includes the plural unless it is obvious that it is meant otherwise.

Further, use of the term “plurality” is meant to convey “more than one” unless expressly stated to the contrary.

As used herein, qualifiers like “substantially,” “about,” “approximately,” and combinations and variations thereof, are intended to include not only the exact amount or value that they qualify, but also some slight deviations therefrom, which may be due to manufacturing tolerances, measurement error, wear and tear, stresses exerted on various parts, and combinations thereof, for example.

The use of the term “at least one” or “one or more” will be understood to include one as well as any quantity more than one. In addition, the use of the phrase “at least one of X, V, and Z” will be understood to include X alone, V alone, and Z alone, as well as any combination of X, V, and Z.

The use of ordinal number terminology (i.e., “first”, “second”, “third”, “fourth”, etc.) is solely for the purpose of differentiating between two or more items and, unless explicitly stated otherwise, is not meant to imply any sequence or order or importance to one item over another or any order of addition.

Finally, as used herein any reference to “one embodiment” or “an embodiment” means that a particular element, feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment.

In one embodiment in accordance with the present disclosure, a method for capturing aerial images comprises: determining, with at least one of a controller of an unmanned aerial vehicle and a processor of a remote station, a flight plan of the unmanned aerial vehicle, the flight plan configured such that the unmanned aerial vehicle and fields of view of an image capture device of the unmanned aerial vehicle are restricted to an area within boundaries of a geographic location identified by coordinates of the geographic location; and executing, with the unmanned aerial vehicle, the flight plan; and capturing, with the image capture device, one or more aerial images solely within the boundaries of the geographic location while executing the flight plan.

In one embodiment, executing the flight plan is carried out automatically by the controller of the unmanned aerial vehicle.

In one embodiment, executing the flight plan is at least partially carried out by an operator utilizing the human-machine interface module of the remote station, and further comprising: receiving, by the remote station from the communications system, one or more first non-transitory signal indicative of position of the unmanned aerial vehicle; and transmitting, from the remote station to the communications system of the unmanned aerial vehicle, one or more second non-transitory signal indicative of instructions for navigation of the unmanned aerial vehicle to maintain the unmanned aerial vehicle within the boundaries.

In one embodiment, a method comprises receiving aerial images captured by one or more unmanned aerial vehicle; receiving metadata associated with the aerial images captured by the one or more unmanned aerial vehicle; geo-referencing the aerial images based at least in part on a geographic location of a surface to determine geographic coordinates of pixels of the aerial images; receiving a geographic location from a user; retrieving one or more of the aerial images associated with the geographic location based on the determined geographic coordinates of the pixels; and displaying to the user one or more overview image depicting the geographic location and overlaid with one or more icons indicative of and associated with the retrieved aerial images associated with the geographic location.

In one embodiment, the metadata includes orientation, attitude, and bearing of one or more image capture device that captured the one or more aerial image, and wherein geo-referencing the aerial images based at least in part on a geographic location of a surface to determine geographic coordinates is geo-referencing the aerial images based at least in part on a geographic location of a surface and using the orientation, attitude, and bearing of the image capture device to determine the geographic coordinates of objects depicted in the one or more aerial image.

In one embodiment, the method further comprises receiving a selection from the user of one of the icons; and displaying the retrieved aerial image associated with the icon. The geographic location from the user may be in a form of three or more geographic points forming a polygon. The method may further comprise creating a three dimensional polygon based on the polygon and a predetermined height dimension; wherein retrieving one or more of the aerial images associated with the geographic location based on the determined geographic coordinates further comprises retrieving one or more of the aerial images associated with the geographic location based on the three dimensional polygon.

In one embodiment, a method comprises receiving aerial images captured by one or more image capture device on one or more unmanned aerial vehicle, the aerial images depicting only objects above the ground; receiving metadata associated with the one or more image capture device at the time the aerial images were captured, the metadata including latitude and longitude of the one or more image capture device and one or more of altitude, orientation, attitude, and bearing of the one or more image capture device; receiving information indicative of a location of a region of interest; and geolocating one or more of the aerial images, thereby associating one or more of the geolocated aerial images with the region of interest. Geolocating the one or more aerial images may be based at least in part on correlating the information indicative of the location of the region of interest and the metadata associated with the one or more image capture device at the time the aerial images were captured.

In one embodiment, the metadata associated with the one or more image capture device may further include one or more of sensor size of the one or more image capture device, focal length of the one or more image capture device; pixel pitch of the one or more image capture device, and distortion parameters of the one or more image capture device.

In one embodiment, a method comprises receiving aerial images captured by one or more unmanned aerial vehicle and time data indicative of a time the aerial images were captured; receiving metadata captured by the one or more unmanned aerial vehicle including time data indicative of when the metadata was captured; associating the metadata with the aerial images based at least in part on matching the time data of the metadata with the time data of the aerial images; geo-referencing the aerial images based on a geographic location of a surface to determine geographic coordinates of pixels for ground locations and objects depicted in the aerial images; receiving a geographic location from a user; retrieving one or more of the aerial images associated with the geographic location based on the determined geographic coordinates; and displaying to the user one or more overview image depicting the geographic location and overlaid with one or more icons indicative of and associated with the retrieved aerial images associated with the geographic location.

In one embodiment, a method comprises receiving non-standardized metadata captured by an unmanned aerial vehicle and associated with one or more image captured by the unmanned aerial vehicle; transforming the non-standardized metadata into a standardized format; and storing the transformed metadata in a first database associated with the one or more image stored in a second database.

In one embodiment, a method comprises determining, with at least one of a controller of an unmanned aerial vehicle and a processor of a remote station, a flight plan of the unmanned aerial vehicle, the flight plan configured such that the unmanned aerial vehicle and fields of view of an image capture device of the unmanned aerial vehicle are restricted to an area within boundaries of a geographic location identified by coordinates of the geographic location; executing, with the unmanned aerial vehicle, the flight plan; and capturing, with the image capture device, one or more aerial images solely within the boundaries of the geographic location and restricted to fields of view in within the boundaries while executing the flight plan. Executing the flight plan may be carried out automatically by the controller of the unmanned aerial vehicle. Executing the flight plan may be at least partially carried out by an operator utilizing a human-machine interface module of the remote station, and further comprise receiving, by the remote station, one or more first non-transitory signal indicative of position of the unmanned aerial vehicle; and transmitting, from the remote station to a communications system of the unmanned aerial vehicle, one or more second non-transitory signal indicative of instructions for navigation of the unmanned aerial vehicle to maintain the unmanned aerial vehicle within the boundaries.

In one embodiment, a method comprises receiving aerial images captured by one or more unmanned aerial vehicle; receiving metadata associated with the aerial images captured by the one or more unmanned aerial vehicle; geo-referencing the aerial images based at least in part on a geographic location of a surface to determine geographic coordinates of pixels of the aerial images; receiving a geographic location from a user based on selection by the user of one or more pixels of a first one of the aerial images, the geographic location being above the ground; and retrieving one or more of second ones of the aerial images associated with the geographic location from the user based on the determined geographic coordinates of the pixels.

In one embodiment, the geographic location from the user may be in a form of three or more geographic points based on selection by the user of three or more pixels forming a polygon of the first one of the aerial images.

In one embodiment, the first one of the aerial images may include a depiction of a structure and the geographic location from the user in the form of three or more geographic points forming a polygon may be located on the structure in the first on of the aerial image.

In one embodiment, the first one of the aerial images may include a depiction of a structure and the geographic location from the user in in a form of one or more elements of the structure chosen by the user in the first on of the aerial image.

In one embodiment, the one or more elements of the structure may be chosen from the group consisting of a wall, a roof plane, a roof, a floor, a door, an intersection, a cross-section, and a window.

Referring now to the drawings, FIG. 1 is a block diagram of an exemplary embodiment of an unmanned aerial system (UAS) 10 in accordance with the present disclosure. The UAS 10 may comprise one or more Unmanned Aerial Vehicle (UAV) 12. In some embodiments the UAS 10 may further comprise one or more remote station 14. In one embodiment, one or more remote operator 16 may interact with the remote station 14. The remote station 14 may serve a range of functions, from simply receiving data from the UAV 12, up to and including completely controlling all functions of the UAV 12. Further, it will be understood that the UAS 10 may comprise a plurality of UAVs 12 and/or a plurality of remote stations 14, working in pairs separately, or working together in any combination, for example, as shown in FIG. 2. The UAS 10 may comprise two or more UAVs 12 working in tandem and/or independently.

In one embodiment, the UAS 10 may comprise a transponder system (not shown) configured for transmitting signals to other aircraft, the signals comprising information regarding the UAS 10 and/or location of the UAS 10 or UAV 12. The transponder system may be located partially or completely in one or both of the UAV 12 and the remote station 14.

In one embodiment, as illustrated in FIG. 3, the UAS 10 may further comprise a case 17. The case 17 may be used to store and transfer the UAV 12 and/or the remote station 14. Additionally, or alternately, the case 17 may be part of the remote station 14. Additionally, or alternately, the case 17 may be used as part of pre-flight check(s). For example, the case 17 may be used to weigh down the UAV 12 for a power-up check and provide targets for a collision detection diagnostic phase.

The case 17 may also contain actuators (not shown) to move the UAV 12 on the various axes to test how the UAS 10 reacts to changes in attitude. As one non-exclusive example, the UAV 12 is secured to the case 17 such that the UAV 12 may be moved to allow roll, pitch, and yaw. The UAV 12 may be connected to the case 17 via one or more gimbal 21, a nested gimbal, and/or a gimbal lock. A gimbal lock restricts one degree of freedom in a multi-dimensional, multi-gimbal mechanism having “n” gimbals and thus “n” degrees of freedom. The gimbal lock restricts the axes of “n-1” gimbals. For example, in a three-gimbal system, two of the three gimbals are driven into a parallel configuration, “locking” the system into rotation in a degenerate two-dimensional space.

In one embodiment, multiple servos and/or motors may rotate the UAV 12 across each degree of freedom (roll, pitch, and yaw) in a series of tests to verify that the correct power is provided to the correct component of the UAV 12 to compensate for the motion, thereby testing flight-worthiness of the UAV 12.

As illustrated in FIG. 4, in one embodiment, the UAS 10 may further comprise a tether 18 for tethering the UAV 12 to a base 19. In one embodiment, the remote station 14 and/or the case 17 may act as the base 19. In one embodiment, power may be provided through the tether 18 using step up/step down transformers (not shown).

In one embodiment, the UAS 10 may employ software-based distance and/or altitude limits to limit and/or control the use of the UAV 12 to a control range. For example, the operator 16 may set a maximum distance limit in the UAV 12 and/or the remote station 14 so the UAV 12 will not go beyond the control range. And/or the operator 16 may set a maximum above ground limit in the UAV 12 and/or remote station 14 so the UAV 12 will not go above a set altitude, for example 400 feet above the ground. In one embodiment, the maximum altitude limit is set based on Federal Aviation Administration rules. For example, the remote station 14 and/or the UAV 12 may be programmed with data indicative of a particular type of air space and to restrict the use of the UAV 12 to that particular type of air space. For example, the particular type of air space could be “class G” air space to substantially prevent the UAV 12 from interfering with air craft in another type of air space (such as other air space classes).

In one embodiment, the UAV 12 may automatically return to a predetermined home location and/or to the remote station 14 if there is a failure. For example, if components of the UAV 12 fail or if the signal from the remote station 14 fails, the UAV 12 may automatically return to the home location and/or to the remote station 14.

UAV 12:

As shown in FIGS. 2 and 5, the UAV 12 may comprise an airframe 20, a controller 22, a communications system 24, a power system 26, a propulsion system 28, and an avionics system 30. In some embodiments, the UAV 12 may comprise a navigation system 32, or the navigation system 32 may be partially or completely in the remote station 14. In some embodiments, the UAV 12 may comprise one or more Electronic Speed Control (ESC) 34. In some embodiments, the UAV 12 may comprise one or more power bus 36. In one embodiment, the UAV 12 may comprise one or more speed reduction device 150 (for example, as shown in FIG. 18). In some embodiments, the UAV 12 may comprise one or more actuator 38.

The UAV 12 may carry a payload 40. In one embodiment, components of the UAV 12 are sized and specified to safely carry the weight of the desired payload 40 and to meet specifications to withstand wind forces and to reduce the weight of the UAV 12. Additionally, since the weight of the UAV 12 is related to the kinetic energy of the UAV 12, a UAV 12 with a reduced weight has less kinetic energy than a heavier weight UAV 12, and therefore minimizes damage in the event of a crash of the UAV 12.

The UAV 12 may comprise one or more image capture device 42 and/or may carry one or more image capture device 42 as part of the payload 40. Nonexclusive examples of image capture devices 42 include cameras (capable of detecting visible and non-visible ranges of light), infrared sensors, radar, and sonar. The image capture device 42 may capture images 44. The UAV 12 may transmit the images 44 to the remote station 14 and/or to a remote system (not shown), and/or store the images 44, and/or process (partially or fully) the images 44 onboard the UAV 12. Nonexclusive examples of processing the images 44 may include partially or completely georeferencing one or more images 44, geolocating one or more images 44, reviewing one or more images 44 for abnormalities, performing quality control of one or more images 44, tie-pointing (manual/automatic) to relate adjacent images 44, bundle adjustments, 3D point cloud generation from 2D images 44, mosaic generation from the images 44, and/or color-balancing one or more images 44.

In one embodiment, components of the UAV 12 may be tightly integrated to reduce size and weight of the UAV 12. For example, as illustrated in FIG. 6, the controller 22, the communications system 24, the ESCs 34, the power bus 36, and/or components of the power system 26 (e.g. motors) may be integrated into one or more printed circuit board (PCB) 50 or a hybrid PCB and integrated circuit. Wires may be substituted with PCB traces, thus reducing or eliminating the number of wires and connectors required.

Additionally, or alternately, all or some of the payload 40, for example, the image capture device 42, may be integrated on one or more shared PCB 50, as shown in FIG. 7, for example, with the power bus 36 and/or controller 22.

In one embodiment, as shown in FIG. 8, components of the power system 26 may be mounted directly to the PCB 50, along with other components, such as the power bus 36 and/or the controller 22. Additionally, or alternately, wires may be used to connect the power system 26 to the Electronic Speed Controls 34.

UAV Airframe 20:

Returning to FIG. 2, it will be understood that any type of aircraft airframe may be used as the basis of the airframe 20 of the UAV 12. Non-exclusive examples of types of UAVs 12 having different airframes 20 include a fixed-wing UAV 12 a having a front or rear propeller, a fixed-wing UAV 12 b having multiple wing propellers, a helicopter type UAV 12 c, a multi-rotor UAV 12 d, a tilt-rotor UAV 12 e, a jet-type UAV 12 f, and a blimp-type UAV 12 g. In one embodiment, the airframe 20 of the UAV 12 g may have a blimp-like design in which the airframe 20 encloses lighter-than-air gas.

The airframe 20 of the UAV 12 may have one or more control surfaces 60 such as elevators, rudders, flaps, slats, and/or ailerons. The control surfaces 60 may have one or more servomechanism (not shown).

The airframe 20 of the UAV 12 may have attachments to carry the payload 40 and/or the payload 40 may be integrated into the airframe 20 of the UAV 12.

In one embodiment, the PCB 50 may also form a section of the airframe 20.

The airframe 20 may be configured to absorb energy, such as energy generated in a collision. In one embodiment, as illustrated in FIG. 9, the airframe 20 may include padding 70 that meets OSHA 1910.135b and the cited ANSI requirements for head protection. The padding 70 may substantially cover one or more exterior surfaces of the airframe 20. The padding 70 may be formed of foam or other appropriate padding material. In one embodiment, the airframe 20 is completely or partially composed of foam or other appropriate padding material.

In one embodiment, as illustrated in FIGS. 10-12, the airframe 20 may include a bladder system 72 having air bladders 74. The air bladders 74 may substantially cover the airframe 20. The air bladders 74 may weigh less than padding 70.

In one embodiment, the air bladders 74 may have an un-inflated state (FIG. 10) and an inflated state (FIG. 11). In the inflated state, the air bladders 74 may encompass all or part of an exterior of the UAV 12 to protect the UAV 12 from impact with other objects, as well as to protect other objects from impact with the UAV 12. The air bladders 74 may be automatically and/or manually (remotely) switched to the inflated state if the UAV 12 is out of control. In one embodiment, the controller 22 may monitor the power system 26, the propulsion system 28, the avionics system 30, and/or the navigation system 32. If the controller 22 determines the UAV 12 is outside of predetermined parameters for one or more of the systems, the controller 22 may signal the air bladder system 72 to switch the air bladders 74 to the inflated state from the uninflated state. In one embodiment, the air bladders 74 may be automatically triggered to the inflated state when power is lost to one or more of the systems in the UAV 12.

In one embodiment, as shown in FIG. 12, the bladder system 72 may comprise one or more air bladders 74, a bladder system control 76, and one or more containers 78 containing compressed gas 79. The air bladders 74 may be inflated with the compressed gas 79 from the containers 78 by the bladder system control 76. The air bladders 74 may be automatically and/or manually (remotely) switched to the inflated state if the UAV 12 is out of control, via the bladder system control 76. In one embodiment, the bladder system control 76 may monitor the power system 26, the propulsion system 28, the avionics system 30, and/or the navigation system 32. If the bladder system control 76 determines the UAV 12 is outside of predetermined parameters for one or more of the systems, the bladder system control 76 may signal the air bladder system 72 to switch the air bladders 74 to the inflated state from the uninflated state.

In one embodiment, the airframe 20 may include both padding 70 and air bladders 74.

In one embodiment, sections of, or all of, the airframe 20 may be designed to break apart or compress on impact to help absorb the energy of a collision. This might include spring loading, gas loading, compressible materials, or weak points in the airframe 20 that are meant to break and/or collapse during a collision.

As illustrated in FIG. 13, in one embodiment, the UAV 12 may comprise a closed loop sensor 80 surrounding at least a portion of the airframe 20. The closed loop sensor 80 comprises an electrical circuit 82 surrounding at least a portion of the airframe 20. The closed loop sensor 80 works to signal the controller 22 if there is a break in the electrical circuit 82. For example, if the airframe 20 is damaged or is in a collision, there is a disruption in the electrical circuit 82 of the closed loop sensor 80, and the controller 22 and/or the remote station 14 receive a signal indicating the airframe 20 has been compromised. Then the controller 22 and/or the remote station 14 may shut down the power system 26 and/or emit a warning to the remote operator 16 and anyone in the vicinity. The warning may be in any form, non-exclusive examples of which are an audible and/or visual warning.

UAV Controller 22:

Turning now to FIG. 14, a block diagram of an exemplary controller 22 is shown. The controller 22 may control the functions of, and/or receive data from, the communications system 24, the power system 26, the propulsion system 28, the avionics system 30, the navigation system 32, and/or the ESC(s) 34. In one embodiment, the controller 22 may use data from the avionics system 30 or elsewhere (for example, an airspeed sensor, one or more down facing camera, GPS speed, etc.) to detect and limit the speed of the UAV 12. In one embodiment, the controller 22 may contain a maximum speed setting and/or altitude setting for the UAV 12.

In one embodiment, the controller 22 may include one or more computer processor 90 and/or field-programmable gate array (FPGA) 92, one or more drive 94, one or more user input device 96, and one or more non-transitory memory 98. In one embodiment, the controller 22 may have an image capture module 100.

The computer processors 90 and/or FPGAs 92 may be programmed or hardwired to control the UAV 12 and/or to interpret and carry out commands from the remote station 14 to control the UAV 12. In one embodiment, the controller 22 may be configurable to perform specific in-flight functions. The controller 22 may receive flight control instructions from the remote station 14 (or elsewhere), control relevant flight control mechanisms (such as through the power system 26, propulsion system 28, navigation system 32, and/or avionics system 30), and/or provide feedback information (e.g., telemetry information) to the remote station 14 and/or other device(s).

The drives 94 and their associated computer storage media such as removable storage media (e.g., CD-ROM, DVD-ROM) and non-removable storage media (e.g., a hard drive disk), may provide storage of computer readable instructions, data structures, program modules and other data. The drives 94 may store and include an operating system, application programs, program modules, and one or more database storing various data, nonexclusive examples of which include image data, position data, flight control instructions data, flight path data, past flight data, sensor data, and navigation data.

The controller 22 further may include one or more user input device 96, through which a user may enter commands and data. Non-exclusive examples of input devices 96 may include an electronic digitizer, a microphone, a keyboard, and a pointing device such as a mouse device, trackball device or touch pad device. Other input devices 96 may include a joystick device, game pad device, satellite dish, scanner device, or the like.

In one embodiment, the controller 22 may stream data (live or delayed feed) utilizing the communications system 24 to the remote station 14, or other site(s) or vehicle(s), and/or may store data in the one or more non-transitory memory 98. In data streaming applications, the controller 22 may transmit real-time video or data to the remote station and/or to points worldwide. The UAV 12 may have Internet connectivity (for example, through an Inmarsat satellite) and may transmit data directly over the Internet.

In some embodiments, the image capture module 100 may transmit captured images 44 to the remote station 14 or other device through the communication system 24, store the captured images 44 in the memory 98, and/or process the captured images 44. Non-exclusive examples of processing of captured images are described in U.S. Pat. No. 8,477,190, issued Jul. 2, 2013, titled “Real-Time Moving Platform Management System;” U.S. Pat. No. 8,385,672, issued Feb. 26, 2013, titled “System for Detecting Image Abnormalities;” U.S. Pat. No. 7,424,133, issued Sep. 9, 2008, titled “Method and Apparatus for Capturing, Geolocating and Measuring Oblique Images;” and U.S. Patent Publication US20150221079A1, published Aug. 6, 2015, titled “Augmented Three Dimensional Point Collection of Vertical Structures;” all of which are hereby incorporated by reference in their entirety herein.

The image capture module 100 and/or the remote station 14 may also be used to adjust operational parameters, such as resolution, of the image capture device 42. For example, the image capture module 100 and/or the remote station 14 may transmit one or more signal to the image capture device 42 indicating a change to operational parameters.

The memory 98 of the controller 22 may comprise, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which may be used to store the desired information and which may be accessed by the controller or the remote station or other remote processor. Any such computer storage media may be part of the controller 22 and/or the remote station 14.

In one embodiment, the controller 22 may automatically mitigate unexpected flight characteristics. Nonexclusive examples of unexpected flight characteristics include a ground effect (that is, increased lift-force and decreased aerodynamic drag that wings or rotors generate when they are close to a fixed surface), translational lift (i.e. a transitional state present after a helicopter has moved from hover to forward flight), and vortex ring state (i.e. settling with power, in which a rotary UAV 12 settles into its own downwash causing loss of lift). The controller 22 may monitor the power system 26, propulsion system 28, navigation system 32, and/or avionics system 30, to detect unexpected flight characteristics. After detection, the controller 22 may implement counter measures to the detected unexpected flight characteristics, such as sending one or more non-transitory signals to the power system 26, propulsion system 28, navigation system 32, and/or avionics system 30, to control the flight of the UAV 12.

UAV Electronic Speed Controls 34 and Actuators 38:

As previously described and shown in FIG. 5, in some embodiments, the UAV 12 may comprise one or more Electronic Speed Control (ESC) 34. In some embodiments, the ESC(s) 34 may control the operation of the control surfaces 60 of the airframe 20 and/or may control the propulsion system 28, either in conjunction with or instead of the controller 22.

In some embodiments, in which the UAV 12 may comprise one or more actuator 38, the controller 22 and/or the ESC(s) 34 may control the operation of the actuator 38 to actuate the propulsion system 28 (for example, the rotor blade) and/or the control surfaces 60 of the UAV 12. In some embodiments, the ESC 34 may be electrically connected to the controller 22 and the actuator 38. The controller 22 may provide control signals for the ESC 34, which in turn provides actuator signals to the electrically connected actuator 38 so as to actuate the corresponding component of the propulsion system 28 (such as the rotor) or control surface 60 on the airframe 20. In some embodiments, feedback signals can also be provided by the actuator 38 and/or the ESC 34 to the controller 22.

In one embodiment, the number of ESCs 34 is equal to the number of actuators 38 (such as actuators 38 controlling rotors) of the UAV 12. For example, a 4-rotor UAV 12 d may have four actuators 38 and four ESCs 34. In an alternative embodiment, the number of ESCs 34 may be different (more or less) than the number of actuators 38.

In some embodiments, the ESC 34 may control the speed of revolution of the power system 26, such as a motor/generator or an engine.

In some embodiments, the ESCs 34 may be optional. In some embodiments, instead of, or in addition to, the ESCs 34, other types of actuator controllers can be provided to control the operation of the actuators 38, and/or the controller 22 may directly control the control surfaces 60 and/or the propulsion system 28.

UAV Communications System 24:

The communications system 24 of the UAV 12 may communicate with an external system, such as the remote station 14, or other UAVs 12, UASs 10, aircraft, or other vehicles (including ground vehicles or satellites). As depicted in FIG. 5, the communications system 24 may have one or more receiver 110 and one or more transmitter 112. The communications system 24 may have one or more antenna 114 and one or more attenuator 116 for the antenna(s) 114. The attenuator 116 may reduce the strength of a signal from or to the antenna 114. The attenuator 116 may be used for range testing between the UAV 12 and the remote station 14.

An interlock (not shown) may be used to prevent the UAV 12 from taking off with the attenuator 116 in place. The interlock is a device that makes the state of two mechanisms mutually dependent. In one example of an interlock, a sensor is configured to detect that the attenuator 116 is in place. If the attenuator 116 is in place, the UAV 12 is prevented from flying (or flying beyond a predetermined distance) to prevent the UAV 12 from flying beyond the range of the controller 22 with the attenuator 116 attached to the UAV 12. The attenuator 116 may also be affixed to the case 17 such that, when the UAV 12 is removed from the case 17, the attenuator 116 is effectively removed.

The antenna 114 may transmit/receive one or more signal to/from the communications system 24 to communicate with the remote station 14 and/or other UAV 12, aircraft, and/or vehicles.

Non-exclusive examples of communications systems are described in U.S. Pat. No. 8,477,190, issued Jul. 2, 2013, titled “Real-Time Moving Platform Management System,” which is hereby incorporated by reference in its entirety.

UAV Power System 36:

The power system 26, as depicted in FIG. 5, may comprise one or more power generation and/or storage devices. In one embodiment, as illustrated in FIG. 15, the power system 26 may comprise one or more motor 118 or engine (not shown). For example, the engine may be a piston engine or a jet. In one embodiment, the power system 26 may comprise one or more generator and/or a solar power system (not shown) for generating power to supply to the motor 118 or other components of the UAV 12. In one embodiment, the power system 26 may comprise one or more fuel cell (not shown) for generating electrical energy to supply to the motor 118 of the power system 26.

In one embodiment, the motor 118 of the power system 26 may have a light-weight housing 120 made of plastic, or other low-weight material. For example, a motor with a plastic housing may be used (e.g. Emax PM2212 920 KV, Plastic Brushless Motor).

The housing 120 of the motor 118 may be integrated with the airframe 20 and/or a part of the airframe 20. For example, the housing 120 may be molded or printed into the airframe 20, such that fewer or no fasteners (such as screws) are needed to secure the motor(s) 118 to the airframe 20, thus eliminating the potential failure of the fasteners.

In one embodiment, as shown in FIG. 15, the power system 26 may also comprise one or more battery 122 sized to provide power for the desired task set for the UAV 12. Capacity of the battery 122 may be sized for the task with a margin for error. Typically, for small UAVs 12, the battery 122 may make up a significant portion of the weight of the UAV 12. In one embodiment, multiple batteries 122 may be used in conjunction with a base station, such as the remote station 14, such that the UAV 12 can fly back to the remote station 14 and switch out the battery 122. In one embodiment, the battery 122 may be charged from the remote station 14. The battery 122 may be automatically exchanged for another battery at the remote station 14.

The one or more battery 122 may directly plug into a socket of the PCB 50 so there are no wires between the battery 122 and the power bus 36, thus eliminating the added weight of wiring between the battery 122 and the power bus 36.

In one embodiment, the controller 22 and/or the remote station 14 may monitor voltage of the battery 122 to help determine the remaining capacity of the battery 122. Total battery power output may be monitored (both volts and amps) to determine the total power drain from the battery 122. Batteries 122 may have a built-in check (not shown) so the operator 16 can easily check the power level of the battery 122. The built-in check may be a push-button with visual or audible indicators of the level of power of the battery 122.

The controller 22 and/or the remote station 14 may shut down the power system 26 or components of the power system 26, such as the one or more motors 118 (FIG. 15), in the event of a malfunction. For example, the controller 22 and/or remote station 14 may shut down the power system 26 when an impact is detected, such as by an accelerometer; or when there is a disruption in the closed loop sensor 80 surrounding the airframe 20 indicating the airframe 20 has been compromised.

UAV Propulsion System 28:

As shown in FIG. 2, the propulsion system 28 may comprise one or more propulsion device 130, including a combination of different types of propulsion devices 130.

In one embodiment, the one or more propulsion device 130 of the UAV 12 f may be a jet engine.

In one embodiment, the one or more propulsion device 130 may comprise one or more rotor 132. The term “rotor” as used herein refers to a hub with a number of rotating air foils or blades. The rotor 132 may be orientated vertically (such as to provide propulsion), horizontally (such as to provide lift), or may be angularly adjustable (such as a tilt rotor). In one embodiment, the one or more rotor 132 may be comprised of a material that yields when subjected to force, such as in the event of a strike of the rotor 132 against another object. For example, if the rotor 132 strikes an object, the rotor 132 may deflect, bend, or break to absorb the force of the strike.

As shown in FIG. 16, in one embodiment, the propulsion system 28 may further comprise a propeller guard 134. The propeller guard 134 may be connected to and supported by the airframe 20. The propeller guard 134 may surround the rotor(s) 132 with a shroud or a cowling. The propeller guard 134 may cover exposed areas of the rotor(s) 132. In one embodiment, the propeller guard 134 may have openings no longer than one-half inch. The dimensions of the openings may comply with the Occupational Safety Health Administration regulation 1910.212(a)(5), which states in part, “The use of concentric rings with spacing between them not exceeding a one-half inch are acceptable, provided that sufficient radial spokes and firm mountings are used to make the guard rigid enough to prevent it from being pushed into the fan blade during normal use.”

In one embodiment, removing the propeller guard 134 may interrupt electricity to the propulsion system 28. In one embodiment, when the propeller guard 134 is removed, a circuit (not shown) of the power system 26 is interrupted so that the power system 26 is nonoperational, and the rotor 132 is therefore no longer provided power. The propeller guard 134 may include a continuous loop conductor (e.g., conductive ink) (not shown) that substantially covers the outline of the propeller guard 134, such that, in the event that the propeller guard 134 is broken, the conductive path is also broken. When the controller 22 of the UAV 12 detects a break in the propeller guard 134, the UAS (such as the controller 22 and/or the remote station 14) may shut down the power system 26 and/or emit an audible and visual warning to the operator 16 and anyone in the vicinity.

The controller 22 and/or the remote station 14 may shut down the propulsion system 28 or components of the propulsion system 28, such as the rotors 132, in the event of a malfunction. For example, the controller 22 and/or remote station 14 may shut down the propulsion system 28 when an impact is detected, such as by the accelerometer; or when there is a disruption in the closed loop sensor 80 surrounding the airframe 20 indicating the airframe 20 has been compromised.

UAV Avionics System 30 and Navigation System 32:

As shown in FIG. 5, in one embodiment, the UAV 12 may comprise an avionics system 30. In one embodiment, the avionics system 30 may include mechanical and electronic flight control mechanisms such as motor(s), servo(s), fuel control switches, etc. (not shown) associated with various flight operations of the UAV 12. In one embodiment, the avionics system 30 may comprise one or more processor (not shown). In one embodiment, the avionics system 30 may comprise one or more actuators 38.

In one embodiment, illustrated in FIG. 17, the avionics system 30 may comprise one or more sensor 140 _(i) . . . 140 _(i+n). Of course, it will be understood that one or more of the sensors 140 _(i) . . . 140 _(i+n) may be onboard the UAV 12 but outside of the avionics system. Nonexclusive examples of sensors 140 _(i) . . . 140 _(i+n), include a roll sensor, a pitch sensor, a yaw sensor, an altitude sensor (such as an altimeter), a directional sensor, and a velocity sensor. In one embodiment, the avionics system 30 may comprise an inertial measurement unit (IMU) for measuring the velocity, orientation, and/or gravitational forces of the UAV 12. The IMU may include one or more accelerometers and/or gyroscopes.

The sensors 140 _(i) . . . 140 _(i+n) may further comprise an airspeed sensor for determining the relative speed between the UAV 12 and the body of air through which it is travelling. In one embodiment, the sensors 140 _(i) . . . 140 _(i+n) may comprise a pitot sensor comprising both static and dynamic pressure sensors.

The sensors 140 _(i) . . . 140 _(i+n) may comprise one or more altitude sensor, which provides a signal indicative of the altitude of the UAV 12 above sea level and/or above ground. For example, the altitude sensor may comprise a GPS receiver, a magnetometer, a barometric altimeter, etc. Signals from the sensor(s) 140 _(i) . . . 140 _(i+n) may be sent via a power bus (not shown) to the avionics system 30 and/or the navigation system 32.

In previous systems that utilized GPS receivers and/or magnetometers, the GPS receiver and magnetometer were located close to the other electrical components. However, the operation of magnetometers may be affected by interference from other electrical components and/or the GPS receiver. To reduce risk of interference, in one embodiment, the ESCs 34 of the motors 118 may be mounted away from the magnetometer to prevent interference. Additionally, or alternately, the ESCs 34, magnetometer, and/or GPS receiver may be shielded.

In one embodiment, the sensors 140 _(i) . . . 140 _(i+n) may comprise one or more collision detection sensor. Non-exclusive examples of collision detection sensors include an ultra-sonic device, a radar device, a laser device, a sonar device, an imaging device, and a transponder/receiver device. In one embodiment, the one or more collision detection sensor may be utilized by the avionics system 30 to determine position of and avoid collisions with other aircraft, the ground, other structures, trees, and/or other obstacles.

In one embodiment in which the collision detection sensor is a transponder/receiver device, the avionics system 30 may comprise a Traffic Alert and Collision System (TACS) utilizing the collision detection sensor to warn of aircraft within the vicinity of the UAV 12. Such systems are well known by persons having skill in the art, for example, as described in “The Traffic Alert and Collision Avoidance System,” Kuchar and Drumm, Lincoln Laboratory Journal, Volume 16, Number 2, 2007, which is hereby incorporated by reference in its entirety herein. The controller 22 of the UAV 12 and/or the remote station 14 may utilize information from the TACS to change flight paths to avoid collisions with other aircraft.

In one embodiment, the avionics system 30 may comprise a Terrain Awareness and Warning System (TAWS) utilizing one or more sensor 140 _(i) . . . 140 _(i+n), such as the one or more collision detection sensor. The TAWS may signal the controller 22 and/or the remote station 14 when the sensor 140 detects terrain or structures within a predetermined distance of the UAV 12, when the UAV 12 goes outside predetermined flight parameters, and/or when the UAV 12 leaves a predetermined flight path or flight area.

In one embodiment, the navigation system 32 may be located within the UAV 12. Additionally, or alternately, part or all of the navigation system 32 may be located in the remote station 14. The navigation system 32 may plan and/or deploy the flight path of the UAV 12, may determine/receive location coordinates, may determine/receive way points, may determine/receive real world position information, may generate and transmit signals to appropriate components to control the flight of the UAV 12, and so on.

The avionics system 30 and/or the navigation system 32 may monitor the lateral location (latitude and longitude) of the UAV 12 (for example, using a GPS receiver), and/or monitor the altitude of the UAV 12 using the signals from the sensors 140 _(i) . . . 140 _(i+n), and/or may receive information from the remote station 14.

In one embodiment, the controller 22 utilizes information from the avionics system 30 in conjunction with the navigation system 32 to fly the UAV 12 from one location to another. For example, the controller 22 may utilize the information to control the control surfaces 60 of the airframe 20 of the UAV 12 (for example, elevators, ailerons, rudders, flaps, and/or slats).

The avionics system 30 and/or the navigation system 32 may include a memory (not shown) on which location of controlled airspace is stored, or may communicate with an external device, such as an air traffic control station (not shown) or the remote station 14 to receive transmitted data indicating the location of controlled airspace. The avionics system 30 and/or the navigation system 32 may provide signals to the ESC 34 and/or the controller 22 to be used to control the speed of rotation of the rotor 132 or the output of the motor 118 or engine.

The avionics system 30 and/or the navigation system 32 may estimate the current velocity, orientation and/or position of the UAV 12 based on data obtained from the sensors 140, such as visual sensors (e.g., cameras), IMU, GPS receiver and/or other sensors, perform path planning, provide data to the controller 22 (and/or control signals to the actuators 38) to implement navigational control, and the like.

In one embodiment, the UAV 12 may comprise one or more secondary sensors 140 a _(i) . . . 140 a _(i+n) (FIG. 17) and secondary controller 22 a (FIG. 5) that may be implemented to detect a fault in the primary sensors 140 and/or controller 22 and/or to replace functions of failed sensors 140 _(i) . . . 140 _(i+n) or a failed controller 22. The secondary sensors 140 a _(i) . . . 140 a _(i+n) may include redundant sensors comprising one or more accelerometer, gyro, magnetometer, GPS, etc. In one embodiment, the secondary sensors 140 a _(i) . . . 140 a _(i+n) may comprise redundant attitude sensors and control systems.

The secondary sensors 140 a _(i) . . . 140 a ^(i+n) and controller 22 a may be electrically isolated from the primary controller 22 and/or sensors 140 _(i) . . . 140 _(i+n), via opto isolators and/or magnetic relays so a catastrophic failure of the primary controller 22 and/or sensors 140 _(i) . . . 140 _(i+n) does not cascade to the secondary sensors 140 a _(i) . . . 140 a _(i+n) and controller 22 a. If the secondary sensors 140 a _(i) . . . 140 a _(i+n) and controller 22 a detect a failure in the primary sensors 140 _(i) . . . 140 _(i+n) or controller 22, the secondary controller 22 a may shut off a relay that connects the primary sensors 140 _(i) . . . 140 _(i+n) and controller 22 to the power system 26, such as the battery 122. When a fault is detected, a protocol in the controller 22 may decide if it is appropriate for the UAV 12 to attempt to land or shut down immediately.

In one embodiment, the sensors 140 _(i) . . . 140 _(i+n) of the UAV 12 comprise one or more geo-localization sensor. Non-exclusive examples of a geo-localization sensor include a Global Positioning System (GPS), a Global Navigation Satellite System, a hyperbolic radio navigation system (e.g. LORAN), a motion capture system (e.g. such as manufactured by Vicon), a detector of lines and/or optical points of reference on the ground/structures, and an altimeter.

A form of localization, for example, utilizing the geo-localization sensor, may be used to keep the UAV 12 within a specific operation area (referred to as an “operation box” 211) for the current inspection task. The coordinates of the boundary of the allowed operation area (which may be referred to as a “box” or “fence”) may be stored on the UAS 10.

The box 211 may be predetermined. For example, the box 211 may be determined using parcel boundaries, building outlines, cadastre data, and/or other sources of data (e.g. in any appropriate coordinates, such as latitude and longitude) and altitude. The box 211 may be determined on-site by the operator 16 prior to take off of the UAV 12. On-site establishment of the box 211 (i.e. “boxing” or “fencing”) may be done using a handheld device (for example, a smartphone or tablet having GPS capabilities) to obtain the box corners coordinates. For example, the operator 16 may walk to the corners of the box 211 and record/set a point for the corner of the box 211. In one example, the operator 16 may place the points of the box 211 on a map displayed on the handheld device. In one embodiment, the operator 16 may choose or define a radius from a point as the box 211 or a boundary around a point as the box 211. In one embodiment, the operator 16 may define attributes of one or more point (for example, location or title of the point, for example, southwest corner). In one embodiment, the operator 16 may define outlines of structures and/or trees within the box 211. These vertices and/or boundaries may define the outside boundary of a given property, the location of tall obstructions such as trees, and/or the outline of a structure that is to be captured.

The box coordinates and/or outlines of structures or obstructions may then be relayed from the operator 16 (and/or the handheld device) to the UAS 10 and/or the UAV 12 (for example, through Wi-Fi/Bluetooth, or manual download). In one embodiment, the handheld device may be the remote station 14.

The box 211 may be geographical coordinates and/or altitude values that define a geometric shape (e.g. polygon, circle, square, etc.) on and/or above the earth. In one embodiment, the box 211 may have a maximum altitude or z value. The box 211 may be a 3D polygon having a height. The box 211 may be a 2D geometric shape on the ground that extends upwards either to a maximum z height or up to a maximum altitude. The maximum z height or maximum altitude may be based at least in part on government regulations.

The controller 22 may provide instructions to the UAV 12 such that the UAV 12 stays inside the box 211 and does not fly over adjacent or other properties. The controller 22 and/or the remote station 14 may take appropriate action if the remote station 14 and/or the controller 22 detects that the UAV 12 is leaving the operation box 211. For example, navigation coordinates may be provided to direct the UAV 12 away from leaving the operation box 211, and/or the UAV 12 may be directed to land or to fly to the remote station 14. In one embodiment, the data about the box 211 and/or structures/vegetation in the box 211 are integrated into a flight plan for the UAV 12.

The data may also be used by the controller 22 to help ensure the UAV 12 doesn't collide with structures, trees, etc. The data may also be used by the controller 22 to maintain a specific distance from a structure being captured with images/video, so that the images and video will be a consistent sample distance (millimeters per pixel for example). For example, each pixel of the image 44 taken by the camera 42 of the UAV 12 may represent 1 mm on a structure in the image.

UAV Speed Reduction Device 150:

In one embodiment, as illustrated in FIG. 18, the UAV 12 may comprise a speed reduction device 150. Non-exclusive examples of speed reduction devices 150 include air brakes 152 and parachutes 154. The speed reduction device 150 may be deployed automatically or manually when the controller 22 and/or the remote station 14 or operator 16 detects a malfunction in the UAV 12 and/or that the UAV 12 is out of control. Typically, the speed reduction device 150 creates drag to limit the airspeed of the UAV 12 and therefor reduce kinetic energy. In some windy conditions, the speed reduction device 150 may increase the velocity of the UAV 12 by acting as a sail.

The air brakes 152 may be part of the airframe 20 in the form of hard or pliable panels/sails. In one embodiment, the air brakes 152 may be in the form of gas inflated bladders (not shown).

In propeller driven UAVs 12, the rotor 132 may be utilized as the speed reduction device 150.

UAS Remote Station 14:

As illustrated in FIG. 19, in one embodiment, the remote station 14 may comprise components that interface with the unmanned aerial vehicle 12 and/or the remote operator 16 and/or that process data to/from the UAV 12. The remote station 14 may comprise a human-machine interface module 160, one or more processor(s) 162 (hereinafter “the processor”), one or more drive(s) 164 (hereinafter “the drive”), and a remote station communications system 166. In one embodiment, the remote station 14 may comprise one or more antenna(s) 168 (hereinafter “the antenna”). The antenna 168 may transmit/receive one or more signal to/from the remote station communications system 166 to communicate with one or more UAV 12, aircraft, and/or vehicles.

In one embodiment, the processor 162 may comprise one or more of a smartphone, a tablet personal computer, a personal computer processor, and/or other personal computing device.

The remote station 14 may receive/download onboard data from the UAV 12, for example, through the remote station communications system 166. In one embodiment, the onboard data may include images 44 and/or metadata, such as metadata about the images 44, about/from the image capture device 42, and/or about/from the sensors 140.

The remote station 14 may upload commands from the remote station 14 to the UAV 12, for example, through the remote station communications system 166, in order to control functions of the UAV 12 and/or the payload 40 of the UAV 12. The remote station 14 may transmit commands and/or data to the UAV 12. In some embodiments, the remote station 14 may control the UAV 12 in real time in all three physical dimensions. However, in some embodiments the UAV 12 may operate autonomously or with varying degrees of guidance from the remote station 14 and/or the remote operator 16.

In one embodiment, the remote station 14 may provide the remote operator 16 with real time data concerning the UAV 12 and/or data transmitted from the UAV 12 through the human-machine interface module 160. For example, the remote station 14 may provide the operator 16 with flight information necessary to control the flight of the UAV 12. For example, flight information may include cockpit-type control data such as data from the sensors 140 and/or indications of roll, pitch, and yaw angle, navigational view of attitude data, current position of the UAV 12 with coordinates and/or visually, failure of components/systems within the UAV 12, and so on.

The human-machine interface module 160 may be configured for the operator 16 to receive data and to input data and/or commands. In one embodiment, the human-machine interface module 160 may comprise a display displaying a view transmitted from the UAV 12 similar to a view that an onboard pilot would have. The human-machine interface module 160 may include a control panel for remotely piloting the UAV 12. The human-machine interface module 160 may comprise a graphical user interface. The human-machine interface module 160 may comprise user input devices through which the operator 16 may enter commands and data. Non-exclusive examples of input devices may include an electronic digitizer, a microphone, a keyboard, and a pointing device such as a mouse device, trackball device or touch pad device. Other input devices may include a joystick device, game pad device, satellite dish, scanner device, heads-up device, a vision system, a data bus interface, and so on.

The remote station 14 may translate commands from the operator 16 to the UAV 12 to control the flight control surfaces 60 and speed of the UAV 12. In one embodiment, the remote station 14 may translate simplistic inputs from the operator 16 into specific, detailed, precision-controlled flight control of the UAV 12. For example, the operator's 16 movement of a joystick may be translated by the processor 162 into commands and transmitted via the remote station communications system 166 and the communications system 24 of the UAV 12 to the controller 22 of the UAV 12 to adjust the flight control surfaces 60 of the UAV 12 to affect roll, pitch, and yaw.

In one embodiment, the remote station 14 may comprise one or more attenuator 170 on the antenna 168 for range testing. An interlock (not shown) may be used to prevent the UAV 12 from taking off with the attenuator 170 in place on the antenna 168 of the remote station 14. The attenuator 170 may be used for range testing between the UAV 12 and the remote station 14. The interlock is a device that makes the state of two mechanisms mutually dependent. In one example of an interlock, a sensor is configured to detect that the attenuator 116 is in place. If the attenuator 116 is in place, the UAV 12 is prevented from flying (or flying beyond a predetermined distance) to prevent the UAV 12 from flying beyond the range of the controller 22 with the attenuator 116 attached to the UAV 12. The attenuator 116 may also be affixed to the case 17 such that when the UAV 12 is removed from the case 17 the attenuator 116 is effectively removed.

In one embodiment, the drive 164 and associated computer storage media such as removable storage media (e.g., CD-ROM, DVD-ROM) and non-removable storage media (e.g., a hard drive disk), may provide storage of computer readable instructions, data structures, program modules and other data. The drive 164 may include an operating system, application programs, program modules, and one or more database.

In one embodiment, the remote station 14 may be implemented as a portion of a small-form factor portable (or mobile) electronic device such as a portable computing device, a mobile computing device, an application specific device, or a hybrid device that include any of the above functions. The remote station 14 may be implemented as a personal computer including both laptop computer and non-laptop computer configurations. Moreover, the remote station 14 may be implemented as a networked system or as part of a specialized server.

In one embodiment, the remote station 14 may comprise an automatic dependence surveillance-broadcast (ADS-B) device (not shown) such that when a conventional aircraft or another UAV 12 enters the area the operator 16 may be notified and land the UAV 12. Optionally, the controller 22 of the UAV 12 may automatically land the UAV 12 when notified. The ADS-B device may be configured with ADS-B “Out” and/or ADS-B “In”. ADS-B “Out” periodically broadcasts information about the UAV 12, such as identification, current position, altitude, and velocity, through a transmitter, such as the communications system 166 of the remote station 14 (and/or the communications system 24 of the UAV 12). ADS-B “Out” may provide air traffic controllers and other aircraft with real-time position information. ADS-B “In” allows the reception by the UAS 10 of ADS-B data, such as direct communication from nearby aircraft of their identification, current position, altitude, and/or velocity. In one embodiment, the ADS-B device is located in either or both the remote station 14 and/or the UAV 12.

In one embodiment, the remote station communications system 166 may comprise a transmitter and a receiver.

In one embodiment, the remote station 14 may comprise a wireless datalink subsystem. The wireless datalink subsystem may be configured for remote communication with the UAV 12.

In one embodiment, the remote station 14 may further comprise a mobile power system, such as one or more battery (not shown).

UAV 12 and Remote Station 14 Communication

In one embodiment, the communications system 24 of the UAV 12 and the communications system 166 of the remote station 14 are configured to form a connection between the UAV 12 and the remote station 14 using radio frequency protocols that may or may not meet the requirements of a Wi-Fi network.

In one embodiment, the communications system 24 of the UAV 12 and the communications system 166 of the remote station 14 may utilize a cellular network for communication between the UAV 12 and the remote station 14 and/or communication between the UAS 10 and other vehicles and/or systems. In one non-exclusive example, the UAV 12 and/or remote station 14 may have cellular radios via which data may be communicated. A Verizon MiFi 4G LTE Global USB Modem is an example of such a device. The UAV 12 may connect to the cellular network using the modem and send telemetry, images, photos, etc. The UAV 12 may also receive commands/instructions on where to go next, flight plans, and/or what to photograph/video.

In one embodiment, the controller 22 in conjunction with the communications system 24 of the UAV 12 and/or the communications system 166 of the remote station 14 may operate in a networked environment using logical connections to one or more processors, such as a remote processor connected to a network interface. The remote processor may be the processor 162 of the remote station 14, or located all or in part separately from the remote station 14. The remote processor may be a personal computer, a server, a router, a network PC, a peer device or other common network node, and can include any or all of the elements described above relative to the controller. Networking environments are commonplace in offices, enterprise-wide area networks (WAN), local area networks (LAN), intranets and world-wide networks such as the Internet. It should be noted, however, that source and destination machines need not be coupled together by a network(s) or any other means, but instead, data may be migrated via any media capable of being written by the source platform and read by the destination platform or platforms. When used in a LAN or WLAN networking environment, the controller 22 may be coupled to the LAN through the network interface or an adapter.

The network(s) may comprise any topology employing servers, clients, switches, routers, modems, Internet service providers (ISPs), and any appropriate communication media (e.g., wired or wireless communications). A system according to some embodiments may have a static or dynamic network topology. The network(s) may include a secure network such as an enterprise network (e.g., a LAN, WAN, or WLAN), an unsecure network such as a wireless open network (e.g., IEEE 802.11 wireless networks), or a world-wide network such (e.g., the Internet). The network(s) may also comprise a plurality of distinct networks that are adapted to operate together. The network(s) are adapted to provide communication between nodes. By way of example, and not limitation, the network(s) may include wireless media such as acoustic, RF, infrared and other wireless media.

A network communication link may be one nonexclusive example of a communication media. Communication media may typically be embodied by computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and may include any information delivery media. A “modulated data signal” may be a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency (RF), microwave, infrared (IR) and other wireless media. The term computer readable media as used herein may include both storage media and communication media.

Diagnostic Testing

In some embodiments, pre-flight diagnostic testing is employed. In one embodiment, the UAS 10 is programmed such that, when the UAS 10 is initially powered on, the UAV 12 will not operate without first performing a series of diagnostics to verify that all systems are properly calibrated and operating correctly. In embodiments having redundant sensors 140 a (accelerometer, gyro, magnetometer, GPS, etc.), the remote station 14 may prompt the operator 16 (via the human-machine interface module 160, for example, with a text display or an audible voice) to rotate the UAV 12 on different axes. The values from each sensor pair (that is, the primary sensor 140 and the secondary sensor 140 a) may be compared to verify that they match within a predetermined margin of error.

In one embodiment, as part of a pre-flight diagnostic routine the operator 16 may be prompted by the controller 22 and/or the processor 162 to anchor the UAV 12 to a weight or test rig that is heavy or anchored well enough so the UAV 12 may power up the propulsion system 28 to full power and remain secure on the ground. The preflight test may verify one or more of the following parameters: integrity of the propulsion system 28 at full power (for example, integrity of the rotor 132), RPM output, power consumption (for example, by each motor 118), performance of the electronic speed controls (ESCs) 34, yaw torque, health/output power of the battery 122 under load, thrust output from the propulsion system 28 (for example, each motor/propeller), integrity of the airframe 20, etc.

In one embodiment, collision detection diagnostics are employed. As part of a collision detection test, the operator 16 may be prompted to place an object in front of the collision detection sensor(s) to verify that all collision detection systems are working correctly. In one embodiment, the collision detection diagnostics utilize a pre-flight test rig/jig (not shown) so the predetermined distance for collision detection may be checked with precision.

In one embodiment, the diagnostic tests may also involve placing one or more attenuator 116 and/or attenuator 170 on the antenna(s) 114 of the UAV 12 or the antenna(s) 168 of the remote station 14 for range testing. An interlock may be used to prevent the UAV 12 from taking off when the attenuator(s) 116, 170 are in place.

Diagnostic tests also may be used to check environmental conditions and disallow use of the UAV 12 when it is too windy or the temperature is too hot or too cold. This is particularly important for the battery 122 which may have significantly lower power output in cold temperatures.

In one embodiment, in-flight diagnostic testing is employed. During flight operations a series of algorithms may be used to detect faults and suspend flight operations if required. For example, if the controller 22 adjusts power output to a particular motor 118 and does not “see” the intended change in attitude as a result, the controller 22 may assume there is a malfunction or the vehicle is “stuck” and power down all motors 118.

Referring now to FIGS. 20-24, an example of one embodiment of the UAS 10 in use in accordance with the present disclosure will be described. As illustrated in FIG. 20, a property 200 of interest is identified, such as with location information 202. The location information 202 may be in the form of any coordinate system or location information system, including, but not limited to, a street address, a plat location, and/or latitude and longitude coordinates.

In one embodiment, a general location of the property may be provided, and the UAS 10 may then be provided with, and/or determine, specific boundaries 210 of an inspection site of the property 200—that is, of the operation box 211. In one embodiment, the operator 16 may identify the outer boundaries 210 of the inspection site. In one embodiment, the operator 16 may identify two or more points 212 on the outer boundaries 210 of the operation box 211, as illustrated in FIG. 21. The UAS 10 may then determine the outer boundaries 210 of the operation box 211 based on the identified points 212, as shown in FIG. 22. Though FIG. 21 illustrates the outer boundaries 210 of the operation box 211 as square shaped, the outer boundaries 210 may have the shape of any polygon or polygons. The outer boundaries 210 may have a three dimensional shape including, for example, a polygon having a height, or other structure.

As illustrated in FIGS. 23 and 24, the navigation system 32 of the UAS 10 may utilize the outer boundaries 210 to guide the UAV 12 to remain within the outer boundaries 210 of the operation box 211. Further, the UAV 12 may be directed to only capture images 44 of objects/locations within the boundaries 210, thus protecting privacy interests of surrounding properties.

In one embodiment, the navigation system 32 may utilize the coordinates of the boundaries 210 of the operation box 211 to determine a flight plan for the UAV 12 that remains within the operation box 211. The navigation system 32 may provide the UAV 12 geographical coordinates and/or altitude values that define a geometric shape (e.g. a polygon, a circle, a square, etc.) on and/or above the earth for the operation box 211. The navigation system 32 may provide the UAV 12 a maximum altitude or z value. The geometric shape may be a 3D polygon, having a 2D geometric shape on the ground that extends upwards, either to a maximum z height or up to a maximum altitude (such as a maximum altitude allowed by government regulations). In one embodiment, the controller 22 maintains the UAV 12 inside the 3D polygon such that the UAV 12 does not fly over adjacent and/or other properties. In one embodiment, parcel data, building outlines, and other sources of data may be used to define the geometric shape.

In one embodiment, in addition to, or alternatively to, ensuring that the UAV 12 does not leave the operation box 211, the navigation system 32 may ensure that the camera 42 carried by the UAV 12 does not capture data and/or images 44 on any neighboring structures, cars, and/or individuals, etc. In one embodiment, the 3D polygon information and data from attitude sensors on the camera 42 and/or the UAV 12 carrying the camera 42, can be used to ensure that camera 42 does not capture data and/or images 44 on any neighboring structures, cars, and/or individuals, etc. In one embodiment, 3D data about a structure may be used to ensure the camera 42 is oriented in such a way so that only the structure is in the frame of the image 44 when taking the image 44 or video and that neighboring structures, individuals, and/or vehicles are not in the background of the image 44. In one embodiment, 3D data about a neighboring structure may be used to ensure the camera 42 is oriented in such a way so that the neighboring structure is not captured in the image 44.

Further, if the UAV 12 is utilized to capture images 44 with the image capture device 42, the navigation system 32 may also determine the flight plan that keeps the image capture device 42 of the UAV 12 orientated such that the field of view (designated with arrows from the UAV 12 in different positions within the operation box in FIGS. 23 and 24) of the image capture device 42 is solely within the boundaries 210 of the operation box 211, while capturing desired images 44 of the property 200 of interest.

In one embodiment, at one or more instant in time, the controller 22 of the UAV 12 and/or the remote station 14 may compare the position of the UAV 12, based on data from sensors 140, such as the GPS and/or the altimeter, with the coordinates of the boundaries 210 of the operation box 211. If the distance between the position of the UAV 12 and the boundaries 210 is less than or above a predetermined amount, the UAV 12 may be directed to adjust position and/or orientation to maintain the position of the UAV 12 within the boundaries 210. If the UAV 12 is utilized to capture images 44 with the image capture device 42, the orientation and position of the UAV 12, and thus the image capture device 42, may be adjusted such that the field of view of the image capture device 42 is solely within the boundaries 210 of the operation box 211 to respect the privacy of neighbors adjacent to the boundaries 210.

In one embodiment, the UAV 12 may be orientated and positioned such that the image capture device 42 has a field of view that encompasses an object or structure within the boundaries 210.

In one embodiment, the UAS 10 and the image capture device 42 may be utilized in a method to capture aerial images 44 of a structure while avoiding capturing images of neighboring properties.

In one embodiment, the UAS 10 may be utilized to determine one or more ground location and/or one or more surface location. In one embodiment, the UAS 10 may be positioned on the ground/surface location. A location reading from a GPS onboard the UAS 10 may be taken with the UAS 10 on the ground/surface location. The location reading may include the latitude, the longitude, and the altitude above sea level of the UAS 10. The altitude above sea level from the GPS may be designated as a ground/surface elevation point for the latitude/longitude location of the UAS 10. Once the UAS 10 is launched into the air, another GPS reading for the UAS 10 may be taken, including the latitude, the longitude, and the altitude above sea level of the UAS 10. The height of the UAS 10 above the ground/surface may be calculated by subtracting the ground/surface elevation point from the altitude above sea level of the UAS 10 in the air.

Metadata

In one embodiment, the controller 22 and/or the image capture device 42, the one or more sensors 140, and/or the image capture module 100 may capture metadata associated with one or more of the images 44. Nonexclusive examples of metadata include information about and/or from the UAV 12, the one or more sensors 140, and/or the image capture device 42.

Metadata about the image capture device 42 may comprise such data as the attitude of the UAV 12, the attitude of the image capture device 42, and/or the focal length of the image capture device 42, sensor size of the image capture device 42, pixel pitch of the image capture device 42, and/or distortion parameters of the image capture device 42.

The metadata may include information from the avionics system 30 and/or the navigation system 32 such as orientation and/or position of the UAV 12 based on data obtained from the sensors 140, such as the visual sensors (e.g., cameras), IMU, GPS receiver and/or other sensors 140.

The metadata may include data from a GPS and/or data associated with the GPS such as GPS signal strength, number and information regarding available satellites, and so on. The metadata may include data from an IMU and/or data associated with the IMU, such as information about pitch, roll, yaw, acceleration vectors in x, y, z orientations, and acceleration vectors about an x-axis, about a y-axis, and about a z-axis.

In one embodiment, the metadata may be from and/or about other sensors of the UAV 12, non-exclusive examples of which include proximity sensors, LiDAR, methane gas sensors, carbon dioxide sensors, heat sensors, multi-spectral sensors (for example, four-band image sensors capable of detecting and/or recording red, green, blue and near infrared), and hyper-spectral sensors (for example, image sensors capable of detecting and/or recording a larger number of spectrum, including 16 or 32 band image—which may include red, green, blue and near infrared and additional spectrum).

In one embodiment, the metadata may include one or more of the following: whether the image 44 or associated image 44 was captured from the UAV 12, the particular type of the UAV 12 (such as, but not limited to, make, model, and/or an identification number of the UAV 12), whether the image 44 was captured from the ground, whether the image 44 was captured from a moving ground vehicle, whether the image 44 was captured from a manned aircraft, whether the image 44 was captured from some other source, and what type of image capture device 42 was used to capture the image 44.

In one embodiment, the metadata may be embedded in the image 44. In one embodiment, the metadata and the image 44 may be stored together in a single image file. In one embodiment, the image 44 may be part of an image file having an image header. The metadata may be embedded in the image header, such as in the header of a jpeg formatted file. In one embodiment, the jpeg header may be organized in a predetermined format such that the metadata is stored in a consistent manner in the jpeg header. For example, the position of the metadata in the header and/or the format of the title of the metadata in the header may be predetermined for consistency.

In one embodiment, the remote station 14 transforms the image file into a standard format for processing.

In one embodiment, the metadata and the image 44 may be stored in a removable non-transitory memory storage device, such as a memory card. The memory card may be removed from the UAS 10 to download the images 44 and the metadata.

In one embodiment, the images 44 and/or the metadata may be transmitted from the UAS 10 to the remote station 14. The images 44 and/or the metadata may be transmitted wirelessly and/or through a physical connection, such as wires. In one embodiment, the images 44 and/or the metadata may be processed by the processor 162 of the remote station 14.

In one embodiment, the images 44 and/or the metadata may first be downloaded wirelessly from the UAS 10 to the remote station 14. Then the images 44 and/or the metadata may be transmitted through a physical connection to a computer processor device where the images 44 and/or the metadata may be extracted and/or processed. For example, the images 44 and/or the metadata may be transmitted a smartphone, a tablet personal computer, a personal computer processor, and/or other personal computing device.

In one embodiment, the UAS 10 may have an application program interface (API).

In one embodiment, the metadata is captured by the image capture device 42 at the time the image 44 is captured.

In one embodiment, the image capture device 42 captures none of, or less than all of, the metadata. In such a case, some or all of the metadata may be captured by the controller 22, the avionics system 30, the navigation system 32, and/or the sensors 140 of the UAS 10. In such a case, the metadata from the time an individual image 44 is taken is matched with that individual image 44.

In one embodiment, the controller 22 transmits one or more signal to the image capture device 42 instructing the image capture device 42 to capture an image 44. At the same time the image 44 is captured, the controller 22 may record the metadata. The metadata may be combined with the image 44 by the controller 22, or may be combined with the image 44 after the image 44 and the metadata are transmitted from the UAV 12 to the remote station 14.

In one embodiment, the metadata contains time data and the images 44 contain time data, and the metadata may be matched to the images 44 by matching the metadata time data to the image time data.

The metadata may be combined with the images 44 in the header of the image file, such as a jpeg header for a jpeg image file.

Metadata may not be necessary in all analysis scenarios, for example, when visual data from an image is sufficient. However, other creation and/or analyses may benefit from and/or require metadata—for example, creation of a three-dimensional model.

In one embodiment, one or more of the images 44 may be geolocated and/or georeferenced.

Geolocating the image 44 comprises associating the image 44 with a location or structure in a location. One example of use for geolocation of the image 44 is for images 44 depicting objects above the ground without depicting the ground, or without ground location information, or without access to surface location information for the objects depicted. For example, an image may depict a chimney on a roof without depicting the ground location. Metadata can be used to associate the image 44 with a particular location or structure. For example, metadata can be used that is associated with the one or more image capture device 42 at the time the aerial images 44 were captured, such as latitude and longitude of the one or more image capture device 42 and/or one or more of altitude, orientation, attitude, and bearing of the one or more image capture device 42. The metadata can be correlated to the location or structure of interest thereby associating the image 44 with the location or structure of interest.

Georeferencing the images 44 may comprise processing the images 44 to determine and assign geographic location information for the pixels of the images 44. For example, the images 44 may be processed as described in U.S. Pat. No. 7,424,133, issued Sep. 9, 2008, titled “Method and Apparatus for Capturing, Geolocating and Measuring Oblique Images;” and/or U.S. Patent Publication US20150221079A1, published Aug. 6, 2015, titled “Augmented Three Dimensional Point Collection of Vertical Structures;” all of which are hereby incorporated by reference in their entirety herein.

The geographic location information may include geographic coordinates for the ground as well as structures and objects located above the ground in the image 44. The geographic location information for the pixels of the image 44 may be a part of the metadata associated with the image 44.

Georeferencing the images 44 may be based at least in part on one or more known ground points and/or surface points. Nonexclusive examples of known ground points and/or surface points include digital elevation models (DEMs), point clouds, three-dimensional models, individually plotted/mapped points, and tessellated ground planes.

In one embodiment, the images 44 may be georeferenced based at least in part on searching for and locating one or more surface model or point cloud having locations within a predetermined proximity of the location of the UAV 12 and/or in the direction of orientation of the UAV 12. In one embodiment, the images 44 may be georeferenced based at least in part on searching for and locating one or more ground point or ground plane having ground locations within a predetermined proximity of the UAV 12.

An image location system 250 constructed in accordance with the current disclosure is illustrated in FIG. 25. The image location system 250 may comprise a metadata database 252 and an image warehouse database 254 stored in one or more non-transitory computer memory 256. The image location system 250 may further comprise one or more processor 258 and one or more user interface 260.

In one embodiment, the metadata is stored in the metadata database 252 and the images 44 are stored in the image warehouse database 254. Metadata and images 44 may be received from multiple UASs 10 and/or multiple UAVs 12 of various types. The metadata may initially be received in varying formats depending on the type of UAV 12 transmitting the metadata. The metadata may be transformed into a standardized format. The metadata may be stored with a standardized format.

The metadata may be stored in the metadata database 252 and associated with the image 44 and/or the image file. The metadata may include a file path of the associated image 44 and/or the image file.

In one embodiment, one or more of the metadata, the metadata database 252, the images 44, and the image warehouse database 254 may be stored in one or more remote locations, such as cloud storage.

In one embodiment, the metadata database 252 and/or the image warehouse database 254 may be spatial databases. That is, the metadata database 252 and/or the image warehouse database 254 may be structured with spatial (locational) connections such that spatial conclusions and results can be reached. The metadata database 252 and/or the image warehouse database 254 may be able to search for, find, and return to a user data based on an input location. For example, a user may request images 44 within one mile of a location and the metadata database 252 and/or the image warehouse database 254 may return such information. In another example, the user may request images 44 within a polygon drawn on an overview image. In another example, the user may request images 44 based on other location information.

A user may utilize the image location system 250 to locate image(s) 44 and/or metadata for a particular geographic area or structure. In one embodiment, the user may search for images 44 of a structure and/or geographic location by inputting geographic coordinates through the user interface 260. In one embodiment, the user may search for images 44 by choosing one or more points, facets, components, or areas of a structure in an image, floorplan, 2D model, or 3D model, as shown in FIGS. 30-38. In one embodiment, the user may search for images 44 of the structure and/or geographic location by inputting a polygon 268 (such as a 2D or 3D polygon) of geographic coordinates through the user interface 260. In one embodiment, the user may input geographic points, and the processor 258 of the image location system 250 may form the polygon 268 of geographic coordinates from the inputted points.

In one embodiment, as shown in FIGS. 30-34, the polygon 268 may be located by the user on a structure in an image 44. In one embodiment, the polygon 268 may be an area or facet of a structure in an image 44. In one embodiment, the image location system 250 may utilize the polygon 268 in conjunction with the metadata associated with the image 44 and/or a two-dimensional outline and/or a three-dimensional model of the structure in the image 44 to identify the portion of the structure selected by the user. In one embodiment, the image location system 250 may allow the user to further specify a particular area of the structure.

The image location system 250 may search the metadata database 252 for geographic information in the metadata matching, or approximate to, the geographic coordinates entered by the user. The image location system 250 may then display images 44 associated with the metadata matching the geographic coordinates. The displayed images 44 contain pixels having matching geographic coordinates.

In one embodiment, the image location system 250 may search the metadata database 252 for points on the ground that match, or are approximate to, the geographic coordinates entered by the user. In one embodiment, the image location system 250 may search the metadata database 252 for points on the ground that are intersected by or enclosed within the polygon 268.

In one embodiment, the image location system 250 may search the metadata database 252 for points above the ground that match, or are approximate to, the geographic coordinates entered by the user. In one embodiment, the image location system 250 may search the metadata database 252 for points above the ground that are intersected by or enclosed within the polygon 268. Points above the ground may be geographic location points on structures or vegetation above the ground.

In one embodiment, the image location system 250 may return images of the structure. In one embodiment, the image location system 250 may return images that depict the particular area of the structure chosen by the user.

The images 44 may depict structures and/or vegetation without depicting the ground. For example, images 44 taken by an image capture device 42 with a perspective pointed toward the horizon, or at an angle upwards from the horizon, may not depict the ground. In such a case, the image location system 250 may search the metadata for recorded locations of the image capture device 42 in which the image capture device 42 location matches, intersects, or is enclosed in, the inputted coordinates and/or polygon 268.

In one embodiment, the image location system 250 may calculate, and or store, data indicative of points on, in, and/or the outline of, one or more structures and/or vegetation depicted in the images 44, the attitude of the image capture device 42, and the bearing of the image capture device 42 (i.e. the direction the image capture device 42 was pointing when the image 44 was captured). The data can be stored in the metadata database 252. Utilizing the data, the image location system 250 may determine the geographic coordinates (X, Y, and Z) where the view of the image capture device 42 intersects the one or more structure and/or vegetation. The image location system 250 may utilize the intersection geographic coordinates as a geographic marker for the image 44. The image location system 250 may match the inputted geographic coordinates to the intersection geographic coordinates to locate an image 44 depicting a geographic location having geographic coordinates matching or within a predetermined distance relative to inputted geographic coordinates and/or polygon 268.

In one embodiment, a user may search for images 44 with the image location system 250 by inputting a geo-code. For example, the user may enter a street address and receive a property parcel's geometry, that is, a property parcel polygon of the property line of a land parcel or building. The user may use the received property parcel polygon as polygon 268 to input into the image location system 250 to request any images 44 for that polygon, that is, any images 44 that intersect the polygon 268 or that are associated with the property within the polygon.

In one embodiment, the user may search for images 44 with the image location system 250 by selecting the polygon 268 that was formed by the operator of the UAV 12 when establishing boundaries 210 of the operation box 211 when one or more of the images 44 were originally captured by the image capture device 42 of the UAV 12.

In one embodiment, the metadata includes a street address. The street address may be acquired by an operator of the UAS 10. The street address may be associated with the images 44 captured by the UAS 10 while the UAS 10 is operated to capture images 44 at the street address.

In one embodiment, the image location system 250 may process one or more of the images 44 before a user utilizes the image location system 250. In one embodiment, the image location system 250 may create one or more 3D model based on the images 44 and the metadata, calculate one or more virtual nadir camera view, and then create an ortho-mosaic based on the 3D model and virtual nadir camera views.

In one embodiment, the image location system 250 may process one or more of the images 44 and/or the metadata and create one or more three-dimensional point clouds and/or one or more three-dimensional models based at least in part on the images 44 and/or the metadata. In one embodiment, the metadata may be used to produce more accurate results to existing or new models and/or images 44.

In one embodiment, the image location system 250 may process one or more of the images 44 by ortho-rectifying the images and stitching the images 44 together using tie points to create an ortho-mosaic.

In one embodiment, the ortho-mosaic may be divided into tiles (for example, tiles 256×256 in size). The image location system 250 may display one or more tiles to the user, such as when the user views the ortho-mosaic in a web-based browser. The tiles may be in a standardized format for use in multiple types of web-based browsers.

Referring now to FIGS. 26-29, in one embodiment, the image location system 250 may provide multiple images 44 from different perspectives to the user. For example, the image location system 250 may initially provide an overview image 270, such as a top-down (nadir) view, of an entire area/property. In one embodiment, the image location system 250 may display an overlay of the polygon 268 on the overview image 270.

In one embodiment, the image location system may display image tiles or “thumbnail” images 272 (that is, preview images smaller in initial size than the overview image 270) of additional images 44 of the property from different perspectives, different distances, and/or different areas of the property for the user to choose to display. For example, the thumbnail images 272 may be displayed outside of the overview image 270, such as on one side of the overview image 270, as shown in FIG. 27.

As illustrated in FIGS. 27-29, in one embodiment, the overview image 270 and or other images (see FIG. 29) may have icons 274 on and/or beside the overview image 270 to show where the additional images 44 (for example, those represented by the thumbnail images 272) were taken and which direction the image capture device 42 was facing when the additional images 44 were taken.

In one embodiment, the user may select the icon 274 and the image location system 250 may highlight the thumbnail image 272 associated with the icon 274. In one embodiment, the user may select the thumbnail image 272 and the image location system 250 may highlight the portion of the overview image 270 where the image associated with the thumbnail image 272 was captured. In one embodiment, the user may select the icon 274 and the thumbnail image 272 may be displayed. In one embodiment, the user may select the icon 274 and the additional image 44 may be displayed in full.

The overview image 270 provides the user with an overall perspective of where additional images 44 are available. The additional images 44 may depict less than the total area of the property. For example, the image capture device 42 may capture a particular image 44 of a four foot by four foot section of a roof of a structure. If a user views this particular image 44 of the roof section, the user may have difficulty knowing the location of the roof section in relation to the entire structure and/or the property. The image location system 250 may provide links to the overall overview image 270 and/or an ortho-mosaic to help orientate the user. For example, if the particular image 44 of the roof section is to be used for insurance claims, the image location system 250 may give a reference as to where the image capture device 42 was located and orientated when the particular image 44 was captured such that the location of damage to the roof may be ascertained.

In one embodiment, the image location system 250 may display the icon 274 on the overview image 270 to indicate the location of the image capture device 42 and/or the orientation of the image capture device 42 (that is, the direction, the bearing, of the viewpoint of the image capture device) at the time the image 44 was captured. In one embodiment, the icon 274 may include a pie shape indicative of the direction the image 44 was taken (that is, which way the image capture device 42 was facing, the angle view the image capture device 42 had when the image capture device 42 captured the image 44).

In one embodiment, the images 44 may be labeled as to what type of image 44 and/or how the image 44 was captured. For example, the image 44 may be labeled as being captured by the UAV 12. In one embodiment, the thumbnail image 272 and/or the icon 274 may be labeled to indicate the type of image 44 and/or how the image 44 was captured.

In one embodiment, the images 44, the icons 274, and/or the thumbnail images 272 displayed on and/or adjacent to the overview image 270, may be labeled with one or more of the following metadata: whether the image 44 or associated image 44 was captured from the UAV 12, the particular type of the UAV 12 (such as, make, model, and/or an identification number of the UAV 12), whether the image 44 was captured from the ground, whether the image 44 was captured from a moving ground vehicle, whether the image 44 was captured from a manned aircraft, whether the image 44 was captured from some other source, what type of image capture device 42 was used to capture the image 44, or the like.

In one embodiment, the user may select one or more points in the overview image 270 and the image location system 250 may display one or more additional image 44 to show a visual depiction related to the one or more selected points. In one embodiment, the user may select the polygon 268 and the image location system 250 may display all of the additional images 44 available that are encompassed by the polygon 268.

In one embodiment in use, as illustrated in FIGS. 30-38, a user may search for images 44 by selecting an area, a facet 276, a point 278, a component 280, and/or an intersection of a structure in a first image 44 or in a 2D model 282 or 3D model 284. For example, the user may click on an area or facet of the structure, or draw a shape, such as polygon 268 on an area of the structure.

The image location system 250 may detect when the user selects an area or facet 276 of the structure, such as by utilizing two-dimensional outlines and/or three-dimensional models of the structures that are associated with geographic locations on the earth and metadata from the images 44. The image location system 250 may allow the user to further specify a particular area of a structure of interest after a first selection by the user. If the user draws a circle or polygon 268 (or even single clicks to specify a point 278), image location system 250 may further allow the user to specify a particular area, component, and/or element of that structure in which the user is interested. Non-exclusive examples of area, component 280, and/or elements of structures that may be specified include one or more wall, roof plane, roof, floor, door, window, intersection, and cross-section, or portion or combination thereof. The image location system 250 may return images 44 to the user, not just in the geographic proximity to a structure, but that include the area of interest in three dimensional coordinates above the ground and on the structure.

For example, as shown in FIG. 30, the user may select an area, such as polygon 268, on a wall of interest on a structure in an image 44. Using the geo-reference information of the image 44 and/or information indicative of the structure's footprint and geographic location, the image location system 250 can determine that the user selected a section of wall on the structure in the image 44 and not just a point on the ground. The image location system 250 may search the metadata database 252 and/or the image warehouse database 254 for images 44 taken in that locality to discover images 44 that point to that region of the structure, such as images 44 a and 44 b shown in FIGS. 31 and 32. For example, images 44 a and 44 b, may have been taken by the image capture device 42 of the UAV 12 that depict the user selected location in polygon 268, such as by the image capture device 42 when the UAV 12 was in a first location 286 and/or in a second location 288, as shown in FIG. 30.

In one embodiment, the user may simply click on a side or element of the structure in a first image 44 or in a 2D model 282 (as shown in FIG. 38) or 3D model 284 (as shown in FIG. 37) and be quickly presented with thumbnails of the images 44, or the images 44 themselves, that include that side or element of the structure. In one embodiment, search results to the user may include ground shots by an adjuster, street-view, drone, selfie stick, manned aerial, 3D models, etc.

While several embodiments of the inventive concepts have been described for purposes of this disclosure, it will be understood that numerous changes may be made which will readily suggest themselves to those skilled in the art and which are accomplished within the spirit of the inventive concepts disclosed and as defined in the appended claims.

Additionally, it will be understood that components or systems described in certain embodiments may be used in combination with components or systems in other embodiments disclosed herein. Further, it will be understood that other components required for the UAS 10 to be operational are well known in the art such that a person having ordinary skill in the art would readily know how to select and use those components according to the intended use of the UAS 10. 

What is claimed is:
 1. A method, comprising: receiving aerial images captured by one or more unmanned aerial vehicle; receiving metadata associated with the aerial images captured by the one or more unmanned aerial vehicle; geo-referencing the aerial images based at least in part on a geographic location of a surface to determine geographic coordinates of pixels of the aerial images; receiving a geographic location from a user; retrieving one or more of the aerial images associated with the geographic location based on the determined geographic coordinates of the pixels; and displaying to the user one or more overview image depicting the geographic location and overlaid with one or more icons indicative of and associated with the retrieved aerial images associated with the geographic location.
 2. The method of claim 1, wherein the metadata includes orientation, attitude, and bearing of one or more image capture device that captured the one or more aerial image, and wherein geo-referencing the aerial images based at least in part on a geographic location of a surface to determine geographic coordinates is geo-referencing the aerial images based at least in part on a geographic location of a surface and using the orientation, attitude, and bearing of the image capture device to determine the geographic coordinates of objects depicted in the one or more aerial image.
 3. The method of claim 1, further comprising: receiving a selection from the user of one of the icons; and displaying the retrieved aerial image associated with the icon.
 4. The method of claim 1, wherein the geographic location from the user is in a form of three or more geographic points forming a polygon.
 5. The method of claim 4, further comprising creating a three dimensional polygon based on the polygon and a predetermined height dimension; and wherein retrieving one or more of the aerial images associated with the geographic location based on the determined geographic coordinates further comprises retrieving one or more of the aerial images associated with the geographic location based on the three dimensional polygon.
 6. A method, comprising: receiving aerial images captured by one or more image capture device on one or more unmanned aerial vehicle, the aerial images depicting only objects above the ground; receiving metadata associated with the one or more image capture device at the time the aerial images were captured, the metadata including latitude and longitude of the one or more image capture device and one or more of altitude, orientation, attitude, and bearing of the one or more image capture device; receiving information indicative of a location of a region of interest; and geolocating one or more of the aerial images, thereby associating one or more of the geolocated aerial images with the region of interest.
 7. The method of claim 6, wherein geolocating the one or more aerial images is based at least in part on correlating the information indicative of the location of the region of interest and the metadata associated with the one or more image capture device at the time the aerial images were captured.
 8. The method of claim 6, wherein the metadata associated with the one or more image capture device further includes one or more of sensor size of the one or more image capture device, focal length of the one or more image capture device; pixel pitch of the one or more image capture device, and distortion parameters of the one or more image capture device.
 9. A method, comprising: receiving aerial images captured by one or more unmanned aerial vehicle and time data indicative of a time the aerial images were captured; receiving metadata captured by the one or more unmanned aerial vehicle including time data indicative of when the metadata was captured; associating the metadata with the aerial images based at least in part on matching the time data of the metadata with the time data of the aerial images; geo-referencing the aerial images based on a geographic location of a surface to determine geographic coordinates of pixels for ground locations and objects depicted in the aerial images; receiving a geographic location from a user; retrieving one or more of the aerial images associated with the geographic location based on the determined geographic coordinates; and displaying to the user one or more overview image depicting the geographic location and overlaid with one or more icons indicative of and associated with the retrieved aerial images associated with the geographic location.
 10. A method, comprising: receiving non-standardized metadata captured by an unmanned aerial vehicle and associated with one or more image captured by the unmanned aerial vehicle; transforming the non-standardized metadata into a standardized format; and storing the transformed metadata in a first database associated with the one or more image stored in a second database.
 11. A method for capturing aerial images, comprising: determining, with at least one of a controller of an unmanned aerial vehicle and a processor of a remote station, a flight plan of the unmanned aerial vehicle, the flight plan configured such that the unmanned aerial vehicle and fields of view of an image capture device of the unmanned aerial vehicle are restricted to an area within boundaries of a geographic location identified by coordinates of the geographic location; executing, with the unmanned aerial vehicle, the flight plan; and capturing, with the image capture device, one or more aerial images solely within the boundaries of the geographic location and restricted to fields of view within the boundaries while executing the flight plan.
 12. The method for capturing aerial images of claim 11, wherein executing the flight plan is carried out automatically by the controller of the unmanned aerial vehicle.
 13. The method for capturing aerial images of claim 11, wherein executing the flight plan is at least partially carried out by an operator utilizing a human-machine interface module of the remote station, and further comprising: receiving, by the remote station, one or more first non-transitory signal indicative of position of the unmanned aerial vehicle; and transmitting, from the remote station to a communications system of the unmanned aerial vehicle, one or more second non-transitory signal indicative of instructions for navigation of the unmanned aerial vehicle to maintain the unmanned aerial vehicle within the boundaries.
 14. A method, comprising: receiving aerial images captured by one or more unmanned aerial vehicle; receiving metadata associated with the aerial images captured by the one or more unmanned aerial vehicle; geo-referencing the aerial images based at least in part on a geographic location of a surface to determine geographic coordinates of pixels of the aerial images; receiving a geographic location from a user based on selection by the user of one or more pixels of a first one of the aerial images, the geographic location being above the ground; and retrieving one or more of second ones of the aerial images associated with the geographic location from the user based on the determined geographic coordinates of the pixels.
 15. The method of claim 14, wherein the geographic location from the user is in a form of three or more geographic points based on selection by the user of three or more pixels forming a polygon of the first one of the aerial images.
 16. The method of claim 15, wherein the first one of the aerial images includes a depiction of a structure and the geographic location from the user in the form of three or more geographic points forming a polygon is located on the structure in the first on of the aerial image.
 17. The method of claim 14, wherein the first one of the aerial images includes a depiction of a structure and the geographic location from the user in in a form of one or more elements of the structure chosen by the user in the first on of the aerial image.
 18. The method of claim 17, wherein the one or more elements of the structure are chosen from the group consisting of a wall, a roof plane, a roof, a floor, a door, an intersection, a cross-section, and a window. 